Updating, refreshing, and synchronizing the dataset

The dataset is a memory-based. That is, changes made are created in memory – they are in the dataset – but they are not automatically committed to the disk. If changes to the dataset are made and not saved before exiting Family/Part Editor (or before exiting the application), a prompt to save (commit) changes is given. The tools in the Family/Part Editor toolbar are enabled only when actions, such as commit changes or refresh dataset, need to be accomplished.

Tools in the Family/Part Editor toolbar. They are, from left to right: Show Active; Set Active; Commit Changes; Refresh Dataset; and Synchronize Dataset.

The Commit Changes tool () is enabled when changes to the dataset are made. Click it, and changes are committed immediately. Do not click it unless you are ready to commit all pending changes. If there are external changes, a conflict ensues (see Resolving conflicts in the Dataset).

The Refresh Dataset tool () is enabled when the dataset is different from the disk dataset. This happens in one of two ways: (1) changes such as add, delete, or edit parts are made to the dataset; or (2) the disk dataset is changed by someone else, say the system administrator for example. When it is selected, a prompt is given to commit changes. There is no Cancel button for Refresh Dataset. If changes have not been made, but the disk dataset has changed, a prompt is given to accept the new disk dataset. If both have occurred, a prompt to commit the dataset or accept the changed disk dataset is given. There is no merge option (see Resolving conflicts in the Dataset).

The Synchronize Dataset tool () is enabled when the disk dataset has changed from the dataset that is in memory. This can happen if a system administrator updates the disk dataset for example. Click it to update the dataset loaded in memory with the disk dataset. If changes are made to the dataset loaded in memory and there are external changes to the disk dataset, a conflict ensues. Either commit the dataset to the disk dataset, or accept the updated disk dataset. There is no merge option (see Resolving conflicts in the Dataset).

Note: Some firms choose to have a master dataset that resides on a server. Other firms let users manage their own dataset locally. If the dataset resides locally, the dataset should never have to be synchronized since it is not exposed to changes from other users.